@jbonofre Thank you for the quick reply. I'll fix this.
Unfortunately, karaf builds cleanly on Jitpack but afterwards some artifacts cannot be resolved. I'm invastigating this.
I would only add the wrapper if Jitpack is really working.

Do you enable specific maven profiles when building karaf?

Adding Jitpack support is blocked by
jitpack/jitpack.io#8007

@kenwenzel the CI is failure is due to a flaky test on Windows. I'm fixing that in a separate PR.

@jbonofre I have two questions:

• Should we add the Maven wrapper even if the Jitpack support is useless (bug mentioned above will not be fixed)?
• The wrapper scripts are automatically generated via mvn wrapper:wrapper -Dmaven=3.9.16. Therefore no ASF headers are added. In which files are those headers required?

@kenwenzel I'm not against adding the mvn wrapper, but I don't think it's strictly required (we live without it for years 😄 ).
Do you really need it? If not, I would just close this PR.

@jbonofre I need a snapshot (or intermediate) build of Karaf and I thought it is possible via Jitpack. But Jitpack builds require a maven wrapper to work with recent maven versions.
If snapshot builds can be created (and deployed to a public repository) via other ways (Maven Central or Apache Maven repos) then I'm also happy :-) (see also this discussion #2752)

@kenwenzel alright, you have a new snapshot on the way and I'm fixing the weekly build to have up to date snapshots.